F
Farmerbrothers Apps

Responsive Home Layout for Event

Blazor Home Dashboard demonstrates a profile-first home layout with search, checklist, wishlists and shortcut cards. Uses Tailwind utility classes and InputText binding for simple state.

LIVE DEMO
Generated using Instruct UI - An AI for Blazor UI Generation
## What's implemented - Profile card with avatar and action icons - Search input using InputText bound to a string - Checklist list rendered from a POCO collection - Wishlist and Exchange cards with images and status badge - Shortcuts grid of icon tiles and multiple responsive cards - Buttons and visual CTAs for creating exchanges and adding wishlist items ## Key components - InputText with @bind-Value - foreach blocks rendering ChecklistItemModel and ShortcutItemModel - img tags for placeholder images - standard buttons and icon elements (FontAwesome classes) - @code with OnInitialized, LoadChecklistItems, LoadShortcutItems, and simple POCO models ## How it works - Data is loaded in OnInitialized into two in-memory lists (ChecklistItems, ShortcutItems). - Search uses InputText with @bind-Value (searchText) for simple state; no server filtering is wired. - UI rendering relies on foreach loops to create list items and shortcut tiles; click handlers are not implemented. - Images and links use placeholder URLs and Link properties on the models. ## Styling - Tailwind utility classes drive layout and styling (grid, gap-*, rounded-xl, aspect-*, md:/lg: breakpoints). - Responsive two-column layout on large screens: lg:grid-cols-3 with content spanning lg:col-span-2/1. - FontAwesome icon classes supply decorative icons; replace with an SVG icon system if preferred. ## Reuse steps 1. Copy the .razor and model POCO files into a Blazor Server or WASM project. 2. Include Tailwind CSS (or adapt classes to project's CSS) and add FontAwesome (CDN or npm package). 3. Import namespaces if using a non-global namespace and register static assets in index.html/_Host. 4. Replace placeholder images and Link properties with real endpoints or injected services. 5. Add event handlers, navigation (NavigationManager), and optional form validation (EditForm + DataAnnotationsValidator) as needed. ## Limitations & next steps - This is a single page scaffold generated by Instruct UI and contains in-memory sample data; no backend services, auth, or persistence are wired. - No form validation or EditForm is present for input flows; search is local state only. - Accessibility and keyboard focus management need review (icon-only buttons, alt text completeness). - Suggested extensions: hook data services (HttpClient or gRPC), add EditForm for editable user data, implement navigation and click handlers, and integrate real image storage.